Assessor Resource

ICTPRG416
Manage a software component re-use library

Assessment tool

Version 1.0
Issue Date: May 2024


This unit describes the skills and knowledge required to store, document and maintain information and communications technology (ICT) components for reuse.

It applies to individuals in a software development area who are required to manage a library that contains reusable code.

No licensing, legislative or certification requirements apply to this unit at the time of publication.

You may want to include more information here about the target group and the purpose of the assessments (eg formative, summative, recognition)


Evidence Required

List the assessment methods to be used and the context and resources required for assessment. Copy and paste the relevant sections from the evidence guide below and then re-write these in plain English.

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Specify the components for re-use library

1.1 Determine component suitability for reuse by checking its quality, and uses

1.2 Review the size and complexity of re-use components for generalisation, and remove project-specific refinements

1.3 Evaluate the components, including patterns, clusters and frameworks, and break them down into smaller components for greater flexibility or use

1.4 Review the components for duplication, and remove the duplicates

2. Document the re-use library

2.1 Document the components internally and externally, to ensure efficient retrieval

2.2 Document public constants, data structures, component interfaces and limitations

2.3 Document the possible relationships between data structures or objects

2.4 Provide an example code, demonstrating the use of components within the documentation

2.5 Document the development environment configuration

2.6 Provide simple test programs to prove the functionality of the library

3. Set up the library structure

3.1 Classify data structures or objects in a consistent and logical manner

3.2 Ensure that the library has a logical structure so that the user is aware of the library contents, and can understand the logic of how the functionality may be used by another developer

3.3 Develop the structure in such a manner that it avoids redundancy within the library

3.4 Configure the development environment to automate the build of re-use components, and the library

3.5 Take action to ensure that interfaces to the library components are consistent and abstracted

3.6 Add, update, and remove re-use components, as development is undertaken

Evidence of the ability to:

manage a software component re-use library

specify the re-use library components

document the re-use library components

ensure logical structuring and interface facilitate retrieval and use.

Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.

To complete the unit requirements safely and effectively, the individual must:

explain abstraction of code module interfaces

describe the features of component libraries

explain the design paradigms

describe patterns, frameworks and idioms

describe the re-use components, and metrics

describe the content and structure of re-use libraries.

Gather evidence to demonstrate consistent performance in conditions that are safe and replicate the workplace. Noise levels, production flow, interruptions and time variances must be typical of those experienced in the programming and software development industry, and include access to:

the software development environment

technical requirements.

Assessors must satisfy NVR/AQTF assessor requirements.

Submission Requirements

List each assessment task's title, type (eg project, observation/demonstration, essay, assingnment, checklist) and due date here

Assessment task 1: [title]      Due date:

(add new lines for each of the assessment tasks)

Assessment Tasks

Copy and paste from the following data to produce each assessment task. Write these in plain English and spell out how, when and where the task is to be carried out, under what conditions, and what resources are needed. Include guidelines about how well the candidate has to perform a task for it to be judged satisfactory.

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Specify the components for re-use library

1.1 Determine component suitability for reuse by checking its quality, and uses

1.2 Review the size and complexity of re-use components for generalisation, and remove project-specific refinements

1.3 Evaluate the components, including patterns, clusters and frameworks, and break them down into smaller components for greater flexibility or use

1.4 Review the components for duplication, and remove the duplicates

2. Document the re-use library

2.1 Document the components internally and externally, to ensure efficient retrieval

2.2 Document public constants, data structures, component interfaces and limitations

2.3 Document the possible relationships between data structures or objects

2.4 Provide an example code, demonstrating the use of components within the documentation

2.5 Document the development environment configuration

2.6 Provide simple test programs to prove the functionality of the library

3. Set up the library structure

3.1 Classify data structures or objects in a consistent and logical manner

3.2 Ensure that the library has a logical structure so that the user is aware of the library contents, and can understand the logic of how the functionality may be used by another developer

3.3 Develop the structure in such a manner that it avoids redundancy within the library

3.4 Configure the development environment to automate the build of re-use components, and the library

3.5 Take action to ensure that interfaces to the library components are consistent and abstracted

3.6 Add, update, and remove re-use components, as development is undertaken

Evidence of the ability to:

manage a software component re-use library

specify the re-use library components

document the re-use library components

ensure logical structuring and interface facilitate retrieval and use.

Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.

To complete the unit requirements safely and effectively, the individual must:

explain abstraction of code module interfaces

describe the features of component libraries

explain the design paradigms

describe patterns, frameworks and idioms

describe the re-use components, and metrics

describe the content and structure of re-use libraries.

Gather evidence to demonstrate consistent performance in conditions that are safe and replicate the workplace. Noise levels, production flow, interruptions and time variances must be typical of those experienced in the programming and software development industry, and include access to:

the software development environment

technical requirements.

Assessors must satisfy NVR/AQTF assessor requirements.
Copy and paste from the following performance criteria to create an observation checklist for each task. When you have finished writing your assessment tool every one of these must have been addressed, preferably several times in a variety of contexts. To ensure this occurs download the assessment matrix for the unit; enter each assessment task as a column header and place check marks against each performance criteria that task addresses.

Observation Checklist

Tasks to be observed according to workplace/college/TAFE policy and procedures, relevant legislation and Codes of Practice Yes No Comments/feedback
Determine component suitability for reuse by checking its quality, and uses 
Review the size and complexity of re-use components for generalisation, and remove project-specific refinements 
Evaluate the components, including patterns, clusters and frameworks, and break them down into smaller components for greater flexibility or use 
Review the components for duplication, and remove the duplicates 
Document the components internally and externally, to ensure efficient retrieval 
Document public constants, data structures, component interfaces and limitations 
Document the possible relationships between data structures or objects 
Provide an example code, demonstrating the use of components within the documentation 
Document the development environment configuration 
Provide simple test programs to prove the functionality of the library 
Classify data structures or objects in a consistent and logical manner 
Ensure that the library has a logical structure so that the user is aware of the library contents, and can understand the logic of how the functionality may be used by another developer 
Develop the structure in such a manner that it avoids redundancy within the library 
Configure the development environment to automate the build of re-use components, and the library 
Take action to ensure that interfaces to the library components are consistent and abstracted 
Add, update, and remove re-use components, as development is undertaken 

Forms

Assessment Cover Sheet

ICTPRG416 - Manage a software component re-use library
Assessment task 1: [title]

Student name:

Student ID:

I declare that the assessment tasks submitted for this unit are my own work.

Student signature:

Result: Competent Not yet competent

Feedback to student

 

 

 

 

 

 

 

 

Assessor name:

Signature:

Date:

Assessment Record Sheet

ICTPRG416 - Manage a software component re-use library

Student name:

Student ID:

Assessment task 1: [title] Result: Competent Not yet competent

(add lines for each task)

Feedback to student:

 

 

 

 

 

 

 

 

Overall assessment result: Competent Not yet competent

Assessor name:

Signature:

Date:

Student signature:

Date: